Skip to content

RHOAIENG-45141: replace codeflare-operator with kuberay where applicable#977

Merged
openshift-merge-bot[bot] merged 1 commit into
project-codeflare:mainfrom
pawelpaszki:RHOAIENG-45141
Jan 14, 2026
Merged

RHOAIENG-45141: replace codeflare-operator with kuberay where applicable#977
openshift-merge-bot[bot] merged 1 commit into
project-codeflare:mainfrom
pawelpaszki:RHOAIENG-45141

Conversation

@pawelpaszki

@pawelpaszki pawelpaszki commented Jan 13, 2026

Copy link
Copy Markdown
Contributor

Issue link

RHOAIENG-45141

What changes have been made

RHOAIENG-45141: replace codeflare-operator with kuberay where applicable (note that this is a supplement of this PR

Verification steps

Checks

  • I've made sure the tests are passing.
  • Testing Strategy
    • Unit tests
    • Manual tests
    • Testing is not required for this change

@openshift-ci-robot

openshift-ci-robot commented Jan 13, 2026

Copy link
Copy Markdown
Collaborator

@pawelpaszki: This pull request references RHOAIENG-45141 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Issue link

RHOAIENG-45141

What changes have been made

RHOAIENG-45141: replace codeflare-operator with kuberay where applicable (note that this is a supplement of this PR

Verification steps

Checks

  • I've made sure the tests are passing.
  • Testing Strategy
    • Unit tests
    • Manual tests
    • Testing is not required for this change

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot

openshift-ci-robot commented Jan 13, 2026

Copy link
Copy Markdown
Collaborator

@pawelpaszki: This pull request references RHOAIENG-45141 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Issue link

RHOAIENG-45141

What changes have been made

RHOAIENG-45141: replace codeflare-operator with kuberay where applicable (note that this is a supplement of this PR

Verification steps

Checks

  • I've made sure the tests are passing.
  • Testing Strategy
    • Unit tests
    • Manual tests
    • Testing is not required for this change

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@codecov

codecov Bot commented Jan 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.87%. Comparing base (17485ee) to head (c14d2f2).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #977   +/-   ##
=======================================
  Coverage   95.87%   95.87%           
=======================================
  Files          22       22           
  Lines        2132     2132           
=======================================
  Hits         2044     2044           
  Misses         88       88           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Comment thread tests/e2e/rayjob/rayjob_existing_cluster_test.py

@kryanbeane kryanbeane left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm. Only thing to note is that comment about dashboard check (PR shouldn't auto merge without that comment being resolved anyway)

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jan 14, 2026
@openshift-ci

openshift-ci Bot commented Jan 14, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kryanbeane

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 14, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit a384cc3 into project-codeflare:main Jan 14, 2026
20 checks passed
@pawelpaszki pawelpaszki deleted the RHOAIENG-45141 branch January 14, 2026 12:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants